for-developers/module-development/api-changes/v2.1.md (2)

110-151: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Minor: Element type list consistency check.

The graphics overhaul lists 8 element types (text, image, box, line, circle, gauge, group, composite). This matches graphics-elements.md which documents all 8. ✅

One small thing: the "Gauge" description says "value-driven bar/ring meter" but graphics-elements.md also documents orientation: 'horizontal' | 'vertical' | 'ring' — the "bar" covers horizontal/vertical but you might want to be explicit that gauges can be horizontal bars, vertical bars, or rings. Not a blocker, just a thought for clarity.

---

226-226: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Style: "all of the functionality" → "all the functionality"

LanguageTool suggests removing "of" for conciseness. This is a minor style point — "all the functionality" reads more naturally.

- fallback for hosts which don't support all of the functionality of the module API (such as Bitfocus Buttons).
+ fallback for hosts which don't support all the functionality of the module API (such as Bitfocus Buttons).

for-developers/module-development/connection-basics/presets.md (2)

247-309: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

LGTM! The internal actions and feedbacks documentation is comprehensive and matches v2.1.md. The example using internal:wait, internal:logicIf, and internal:customLog demonstrates real usage.

One minor note: the code example at lines 272-304 uses ;[ which is slightly unusual — it's to avoid ASI issues with the leading [. This is fine but might confuse some readers. Maybe add a brief comment?

  ```ts
- ;[
+ // Note the leading semicolon to avoid automatic semicolon insertion issues
+ ;[
    {

---

388-423: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

LGTM! The alternatives section matches v2.1.md and provides a good layered+simple fallback example.

Addressing the static analysis hint at line 392:

- fallback for hosts with a more restrictive drawing, or don't support all of the functionality of the module API (such as Bitfocus Buttons).
+ fallback for hosts with a more restrictive drawing, or don't support all the functionality of the module API (such as Bitfocus Buttons).

user-guide/4_expressions/functions.md (1)

349-388: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider clarifying objectKeys/objectValues behavior with arrays.

The docs note these work on "an object (or array)". For arrays, objectKeys returns string indices ("0", "1"...) which can surprise users expecting numeric indices. A brief note or example would help avoid confusion.